home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20000824-20010305
/
000194_news@columbia.edu _Wed Jan 3 20:12:45 2001.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@columbia.edu>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
by monire.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id UAA01475
for <kermit.misc@cpunix.cc.columbia.edu>; Wed, 3 Jan 2001 20:12:44 -0500 (EST)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id UAA25014
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 3 Jan 2001 20:12:44 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id UAA12165
for kermit.misc@watsun.cc.columbia.edu; Wed, 3 Jan 2001 20:03:13 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: jrd@cc.usu.edu (Joe Doupnik)
Subject: Re: Converting struct tm to time_t
Message-ID: <2aP+8u57Wzic@cc.usu.edu>
Date: 3 Jan 01 17:46:23 MDT
Organization: Utah State University
To: kermit.misc@columbia.edu
In article <87wvcc2qz2.fsf@erlenstar.demon.co.uk>, Andrew Gierth <andrew@erlenstar.demon.co.uk> writes:
>>>>>> "Geoff" == Geoff Clare <gwc@unisoft.com> writes:
>
> Derek> Don't forget to call tzset() after putenv and before mktime
>
> >> SUS sez this is not needed, but I think I recall some older systems
> >> where it was necessary.
>
> Geoff> POSIX.1 has said the same ever since the original 1988
> Geoff> standard. Any systems that do need an explicit tzset() must
> Geoff> be *really* old.
>
> hmm. the only system that could have provoked that recollection would
> have been SCO 3.2.2 or 3.2.4, but it could also just have been down to
> me being overly cautious at the time.
--------
Ok, let me expand the hint on cron to say what I meant in this
thread. Login shells get TZ information somehow, often by means of a
script file run as part of the normal login sequence; call it /etc/profile
if you will in SVRx speak. Not all programs run via a login shell, nor
do all login steps necessarily invoke such TZ-setting scripts. So the
program's environment may be TZ ignorant, because of no formal login or
the pathway was non-standard. Cron is an agent without that formal login
step.
It is unfortunate that timezone information is left to actions at
login or similar user-level configuration steps, but there we are.
Thus the point in the included text above really asks "Did the
current process acquire TZ info?" and the answer is "It all depends."
The second answer is "and it also depends on whether the supporting code
is broken."
Joe D.